Support geojson with altitude - #140
Conversation
According to geojson spec the coordinates of a feature can have 3 dimensions. Before this change the 3rd component of the geometry was misused to store the simplification values of the Douglas-Peucker algorithm. With this change the simplification values are stored in a separate array(sqDist) and the 3rd component of the coordinate remains untouched. Signed-off-by: Nino Kettlitz <1396039+ninok@users.noreply.github.com>
|
Sorry for not responding back then. Closing this as stale — 1) I hesitated because I don't want to add a bunch of code to support a feature that's not in the GeoJSON spec — too hacky while adding real overhead; 2) The codebase has moved a lot since then anyway, so this can't land as is. |
|
@mourner Thanks for responding. Totally forgot about this PR 😅 One comment regarding "a feature that's not in the GeoJSON spec". The [spec]https://datatracker.ietf.org/doc/html/rfc7946) sais:
but point 2, that the codebase has moved a lot, makes this PR obsolete anyways and a new one is quickly created with AI nowadays. |
2 participants
According to geojson spec the coordinates of a feature can have 3 dimensions.
Before this change the 3rd component of the geometry was misused to store the simplification values of the Douglas-Peucker algorithm.
With this change the simplification values are stored in a separate array(sqDist) and the 3rd component of the coordinate remains untouched.
Signed-off-by: Nino Kettlitz 1396039+ninok@users.noreply.github.com